Rely on pulpcore to set up Apache fragments#268
Conversation
|
@ekohl could you rebase this to allow combined testing ? |
80585b2 to
59b3de9
Compare
| pulp: "https://github.com/theforeman/puppet-pulp.git" | ||
| pulpcore: "https://github.com/theforeman/puppet-pulpcore.git" | ||
| pulpcore: | ||
| repo: "https://github.com/ekohl/puppet-pulpcore.git" |
There was a problem hiding this comment.
This obviously needs to be converted in an updated minimum version in metadata.json.
There was a problem hiding this comment.
This needed to be changed before it was merged.
|
Rebased. First commit is pretty unchanged other solving than the merge conflict and adding fixtures.yml. The second commit is an untested change that I think adds support for running Pulpcore on a content proxy. |
0f78ca7 to
e971fcf
Compare
dfba558 to
6911c32
Compare
|
The initial support to run without Foreman is here. I suspect that on EL8 (or without Pulp 2 on EL7) it will fail because it doesn't set the certificates yet. Currently running an EL7 pipeline. |
| $apache_http_vhost = 'pulp-http' | ||
| $apache_https_vhost = 'pulp-https' | ||
| Class['pulp::apache'] -> Class['pulpcore::apache'] | ||
| } else { |
There was a problem hiding this comment.
This else is stand-alone Pulpcore? aka a mirror?
There was a problem hiding this comment.
Yes, but without a Pulp 2 install. I haven't tested this branch yet, but I think you'll hit this if you spin up an EL8 proxy (if we provide the correct parameters).
|
Looks like maybe something isn't entirely configured properly on a mirror: |
|
I noticed the same thing, but couldn't track it down yet. |
This uses theforeman/puppet-pulpcore#105 to avoid defining all parts in this module. This means all functionality can be tested standalone in puppet-pulpcore as atomic units.